As everyone knows hacks released using Vbulletin Options and Usergroup permissions mostly ask people to go to edit its vboptions and/or usergroup permission and then save it wether you make change or not so that it will cache. This is usually problematic, because the end-users don't know what it really does (saving no changes is just saving nothing) and so they forgot hence problem occurs. I believe there's at least 10% of questions asked in the hack thread is about this.


SOLUTION: *apply for install scripts only*

This method can be removed if the coder insert just 2 simple functions:

build_forum_permissions()

Location: adminfunctions.php

This function rebuild the usergroup permission, it's called whenever you edit a usergroup. In the coders side, when they insert new permission by running a sql query this isn't called thus the new permissions are not built.

So then whenever you make a new permission for usergroups, just add a line below and life will be easier:

build_forum_permissions();

build_options()

Location: adminfunctions.php

this is what vb staffs commented for this functions:

// reads options from the setting table and serialises them from the $vboptions[] array
// then saves data back into DB

This function runs 2 queries, one SELECT and one UPDATE.

as above, after inserting new value to the table 'setting' manually just add this line below

build_options();

If you're getting error telling that cannot find build_options() function, place this line above:

require_once('./includes/adminfunctions.php');


I hope I won't see hacks that have this line: "Go to your ACP and edit any usergroup then just press 'save' even you change nothing for the hack to work." ^^

That's all.